home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950329-19950528
/
000190_news@columbia.edu_Thu Apr 20 13:09:24 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA08802
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 20 Apr 1995 21:42:45 -0400
Received: by apakabar.cc.columbia.edu id AA22522
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 20 Apr 1995 21:42:43 -0400
Path: news.columbia.edu!panix!news.mathworks.com!udel!gatech!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Help - MSKermit, WFW 3.11 and missing COM port?
Message-Id: <1995Apr20.190924.48083@cc.usu.edu>
Date: 20 Apr 95 19:09:24 MDT
References: <3mlt7o$hh0@lucy.infi.net> <3mm77g$a8r@apakabar.cc.columbia.edu> <D79o2q.20w@serval.net.wsu.edu>
Organization: Utah State University
Lines: 39
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <D79o2q.20w@serval.net.wsu.edu>, f0030893@unicorn.it.wsu.edu (richard roy drake) writes:
> Frank da Cruz (fdc@watsun.cc.columbia.edu) wrote:
> : In article <3mlt7o$hh0@lucy.infi.net>, Bruce Tarr <btarr@infi.net> wrote:
>
> <snip>
>
> : : other devices are using IRQ 4 or 3. Any known solutions, work arounds or
> : : comments will be appreciated.
> : :
> : Windows is running roughshod over the BIOS communications area. See
> : KERMIT.BWR for a detailed technical explanation. To fix the BIOS
> : communications area, give the following command to Kermit before telling
> : it to SET PORT COM2:
>
> : SET COM2 \x2f8 3
>
> : - Frank
>
>
> I am having the same problem as Bruce Tarr and have read the KERMIT.BWR.
> I put in the SET COM2 \x2f8 3 in the MSCUSTOM.INI file and still get the
> problem. I've played with the speed and flow control settings but since
> it is an intermittant problem, its hard to tell if this changes anything.
---------------
As we've tried to explain, Windows owns the serial port hardware.
Not all hardware is configured as we think, not all works well with Windows
(for a long list of candidate reasons). Thus it falls upon the owner of the
machine to sort out that part of things, alas. A primary rule in this area
is no two pieces of hardware can use the same IRQ wire (whether or not you
"intend" to use the device) nor the same i/o Ports (and those are in blocks
of typically 8-16 adjacent values, so watch out for overlaps).
In addition to these static setup items some serial ports are very
sluggish or picky about first use after a cold boot. Windows is the agent
initializing them, and such initialization steps may produce a non-functional
serial port. See the comments on the SMC big square chip modem as one example.
We wish we could cast a magic spell and your machine would work.
As close as we can come these days is "spend more money, try other hardware."
What a world, and it's not getting better, and it happens to all of us.
Joe D.